Intelligent retrieval of digital assets

ABSTRACT

A technique enables intelligent retrieval of digital assets. The technique involves gathering metadata based on a scan of the digital assets. The gathered metadata includes metadata entries, each metadata entry identifying a particular digital asset and a particular set of digital asset properties of that particular digital asset. The technique further involves storing the digital assets in encrypted form within a digital asset repository of the electronic system after gathering the metadata, and updating a metadata database of the electronic system based on the metadata entries, the metadata database being distinct from the digital asset repository. Accordingly, while the digital assets are stored in the digital asset repository in encrypted form, specific digital assets within the digital asset repository are identifiable in response to a database search of the metadata database since the database search is able to use digital asset properties as searching criteria.

BACKGROUND

Conventional backup systems copy electronic files from primary storage(e.g., a high speed data storage array) to secondary storage (e.g.,disks, tapes, etc.). For example, during a full backup routine, allfiles are copied from primary storage to secondary storage.Additionally, during an incremental backup routine, all files which havechanged or which have been created since the last backup are copied fromprimary storage to secondary storage. Since secondary storage oftenresides at a remote location, the backup files of each backup routineare typically stored in encrypted form thus preventing unauthorizedusers from accessing the information on the backup files.

Similarly, conventional archive systems copy electronic files fromprimary storage to secondary storage. However, once the copies of thefiles reach secondary storage, the original files are removed fromprimary storage to recapture primary storage resources. For example,during an archive routine, all files residing on a particular volume, orolder than a certain date, are transferred onto secondary storage thusfreeing up primary storage disk space, backup resources, etc. for use onother files. Again, since secondary storage often resides at an offsitelocation, the archive files of each archive process are typically storedin encrypted form thus preventing unauthorized users from accessing theinformation on the archive files.

Retrieval of backup or archive files from the secondary storage systemtypically involves manual activity by a system technician or manager.Often, the technician must retrieve a subset of files from a larger set,but does not know up front just which files are relevant. For example,suppose that the secondary storage system receives and stores files frommultiple different client computers as part of a particular backup orarchive routine. Furthermore, for security purposes, suppose that thedata on these files was encrypted by the client computers prior to beingsent from the client computers to the secondary storage system.

To retrieve files relating to certain information (e.g., files relatingto “Company ABC”), the technician enters one or more commands to thesecondary storage system to retrieve all of the files from theparticular backup or archive routine. The secondary storage systemresponds to these commands by decrypting all of the files which werebacked up or archived during that particular backup or archive routineand storing decrypted copies of all of the files in a designatedlocation. The technician is then able to manually navigate through thedecrypted copies of all of the files (e.g., filter, sort, manually openand read, etc.) until the technician finds the files containing thatinformation.

SUMMARY

Unfortunately, there are deficiencies in the above-describedconventional backup and archive routines which, during file retrieval,require the technician to decrypt all of the files from a particularbackup or archive routine, and then manually navigate through thedecrypted files in order to find certain relevant files (e.g., filesrelated to “Company ABC”). Nevertheless, this is the only option for thetechnician since the files on the secondary storage system are encryptedthus preventing the technician from knowing which files on the secondarystorage system are relevant. Under this conventional retrieval approach,a lengthy amount of time and substantial computer resources (e.g.,processing cycles, network bandwidth, etc.) may be required to decryptand store all of the files from the particular backup or archive routine(e.g., the volumes may be large/massive) thus consuming resources whichcould have otherwise been devoted to other work. Additionally, once allof the files from the particular backup or archive routine have beendecrypted, the technician is required to manually sift through all ofthe files for the relevant files which may be prone to error.

Furthermore, even if the technician restores files from an archive thatdoes full indexing of the files, the technician does not have theability to select a subset of the restored files based on particularfile usage properties. For example, the technician cannot find filesbased on the frequencies with which the files were referenced (i.e., howoften the files were accessed). Additionally, the technician cannot findfiles based on which users have accessed the files. Moreover, thetechnician cannot find files based on a historical file trail (e.g., thetechnician cannot determine whether file “A” was copied and became file“B”, whether file “B” was then modified and emailed to another user whostored it as file “C”, etc.). Unfortunately, conventional full indexingarchive systems do not provide the technician with such capabilities.

In contrast to the above-described conventional backup/archive/retrievalapproaches, improved techniques involve gathering metadata regardingfiles from multiple client systems before the client systems encrypt thedata and send the encrypted files to a secondary storage system. Withsuch metadata now available, the user is able to conveniently retrieverelevant files that originally reside on different client systems via asingle operation. Utilizing the gathered metadata, such an operation isable to identify the relevant files from a larger set of files whichresides in a secondary storage system even though the files originatedfrom the multiple different client systems and even though the files arecurrently in encrypted form. For example, a user is capable of carryingout a single e-discovery operation on the gathered metadata to find andmark confidential all files relating to certain information (e.g.,relating to “Company ABC”) without needing to decrypt and manually sortthrough a larger set of files originating from multiple different clientsystems.

Along these lines, improved techniques enable intelligent retrieval ofdigital assets by storing digital assets (e.g., computerized files,voice-mail, instant message logs, e-mail, etc.) in encrypted form alongwith metadata which is gathered prior to digital asset storage. Forexample, encrypted digital assets can be safely stored within a backupor archive system, and the gathered metadata can be entered into adatabase. With the encrypted digital assets stored and the metadataavailable, a user is able to search the metadata based on certaindigital asset properties (e.g., content-based properties, usage-basedproperties, etc.) and thus identify individual digital assets forretrieval even though none of the digital assets has yet been decrypted.Once the individual digital assets have been identified, only thosedigital assets are retrieved (e.g., decrypted and provided to the user).Such operation speeds up the retrieval process, uses fewer resources,and saves the user from having to manually sift through a large numberof files that are of no interest. Additionally, such operation maintainsmaximum security since there is no need to decrypt digital assets whenidentifying the relevant digital assets.

One embodiment is directed to a method for providing access to digitalassets which is performed in an electronic system. The method includesgathering metadata based on a scan of the digital assets (e.g.,collecting metadata from a client device). The gathered metadataincludes metadata entries, each metadata entry identifying a particulardigital asset and a particular set of digital asset properties of thatparticular digital asset. The method further includes storing thedigital assets in encrypted form within a digital asset repository ofthe electronic system after gathering the metadata. The digital assetrepository operates as a protected source of the digital assets. Themethod further includes updating a metadata database of the electronicsystem based on the metadata entries, the metadata database beingdistinct from the digital asset repository. Accordingly, while thedigital assets are stored in the digital asset repository in encryptedform, specific digital assets within the digital asset repository areidentifiable in response to a database search of the metadata databasesince the database search is able to use digital asset properties assearching criteria. Such operation thus provides intelligent retrievalof digital assets.

BRIEF DESCRIPTION OF THE DRAWINGS

The foregoing and other objects, features and advantages will beapparent from the following description of particular embodiments of theinvention, as illustrated in the accompanying drawings in which likereference characters refer to the same parts throughout the differentviews. The drawings are not necessarily to scale, emphasis instead beingplaced upon illustrating the principles of various embodiments of theinvention.

FIG. 1 is a block diagram of an electronic system which providesintelligent retrieval of digital assets.

FIG. 2 is a detailed block diagram of a client device of the electronicsystem of FIG. 1.

FIG. 3 is a detailed block diagram of a server device of the electronicsystem of FIG. 1.

FIG. 4 is a flowchart of a procedure which is performed by theelectronic system of FIG. 1.

FIG. 5 is a flow diagram which illustrates a sequence of activitiescarried out during use of the electronic system of FIG. 1.

DETAILED DESCRIPTION

An improved technique enables intelligent retrieval of digital assets bygathering metadata on client devices prior to encryption (e.g., whilethe digital assets are in use), and then retrieving the digital assetsbased on the gathered metadata while the digital assets are stored inencrypted form. For example, digital assets can be backed up or archivedin encrypted form, and the gathered metadata can be entered into adatabase. With the encrypted digital assets stored and the metadataavailable, a user is able to search the metadata database based oncertain digital asset properties (e.g., content-based properties,usage-based properties, etc.) and thus identify relevant digital assetsfor retrieval without decrypting digital assets (i.e., maximum securityis maintained). Once the relevant digital assets have been identified,only those identified digital assets are retrieved (e.g., decrypted andprovided to the user). Compared to conventional backup and archivesystems which retrieve all files (e.g., perhaps a massive volume), theimproved technique speeds up the retrieval process, uses fewerresources, and saves the user from having to manually sift through alarge number of files that are of no interest.

FIG. 1 shows a block diagram of an electronic system 20 which providesintelligent retrieval of digital assets 22. The electronic system 20includes a client device 24, a server device 26, a secondary storagesubsystem 28, and communications media 30 (e.g., a network). The clientdevice 24, the server device 26, and the secondary storage subsystem 28communicate with each other through the communications media 30 viaelectronic signals 32 (illustrated by the two-way arrow 32 in FIG. 1).Although the electronic system 20 is shown in FIG. 1 as including onlyone client device 24 for simplicity, it should be understood that theelectronic system 20 may include multiple client devices 24 which areprovisioned similarly to that of the client device 24 shown in FIG. 1.

The client device 24 includes client device circuitry 40, originalversions 42 of the digital assets 22, a set of scanning rules 44 (i.e.,one or more scanning rules 44), metadata gathering circuitry 46 andmetadata 48. The server device 26 includes metadata database circuitry60 and a metadata database 62. The secondary storage subsystem 28includes secondary storage circuitry 70 and a digital asset repository72.

During operation, the client device 24 performs useful work on behalf ofa user. In particular, the client device 24 operates as primary storagefor a set of digital assets 22. For example, suppose that the clientdevice 24 is a general purpose computer. In this situation, the clientdevice circuitry 40 may run an application which creates and/or modifiesan electronic file, i.e., an original version 42 of a digital asset 22.Along these lines, the user may run a word processing application whichcreates and/or modifies a text-based electronic document. As a result,an original version 42 of this digital asset 22 now resides on theclient device 24.

Each time a digital asset 22 is accessed on the client device 24, theclient device circuitry 40 updates the metadata 48 to reflect suchaccess. Accordingly, the client device 40 is able to track usageproperties of the digital assets 22 such as access frequency, ownershipand chain of custody, when the last accesses were made, and so on.

At some later time (e.g., during a regularly scheduled backup or archiveprocess), the client device 24 generates encrypted copies 80 of itsdigital assets 22 for storage on the secondary storage subsystem 28. Forexample, the secondary storage subsystem 28 may be a backup system whichperiodically performs a full backup of all of the digital assets 22 oran incremental backup only the digital assets which were created ormodified since the last backup. In this situation, the secondary storagecircuitry 70 of the secondary storage subsystem 28 stores the encryptedcopies 80 of the digital assets 22 in the digital asset repository 72while the original versions 42 continue to reside in the client device24.

As another example, the secondary storage subsystem 28 may be an archivesystem which archives the digital assets 22 of the client device 24after the expiration of a particular amount of time or after a certaindate passes. In this situation, the secondary storage circuitry 70 ofthe secondary storage subsystem 28 stores the encrypted copies 80 of thedigital assets 22 in the digital asset repository 72, and the clientdevice 24 deletes the original versions 42 to free up resources on theclient device 24.

In either the backup system or archive system context, the copiedversions 80 of the digital assets 22 are safely stored for possiblesubsequent retrieval. Since the copied versions 80 were encrypted by theclient device 24 (e.g., using standard encryption techniques),unauthorized users are prevented from accessing the information on thecopied versions 80, i.e., an unauthorized user cannot successfullyretrieve digital assets 22 from the secondary storage subsystem 28.Accordingly, the digital asset repository 72 operates as a protectedsource of the digital assets 22.

Further details of the intelligent retrieval aspects of the electronicsystem 20 will now be provided. Generally, the server device 26coordinates and manages collection of the metadata 48 from each clientdevice 24, by updating the metadata database 62 with digital assetproperty information described by the metadata 48. Such informationpreferably includes content-based properties and usage-based propertiesof each digital asset 22 stored in the digital asset repository 72 ofthe secondary storage subsystem 28. As a result, a user (e.g., anadministrator, an end-user at a client device 24, etc.) can search themetadata database 62 to identify digital assets 22 having specificproperties, and then retrieve only the identified digital assets 22 fromthe digital asset repository 72.

To this end, the client device 24 undergoes configuration by the serverdevice 26 before the client device 24 generates the encrypted versions80 for storage on the secondary storage subsystem 28. In particular, themetadata gathering circuitry 46 of the client device 24 sends a requestmessage 90 to the server device 26 asking the server device 26 whetherthe server device 26 has any new scanning rules 44. Such a requestmessage 90 can be sent periodically from the client device 24 to theserver device 26. If the client device 24 does not yet have any scanningrules 44 or if the server device 26 has new scanning rules 44 which aredifferent than those currently existing in the client device 24, themetadata database circuitry 60 of the server device 26 provides aresponse message 92 containing the new scanning rules 44 to the clientdevice 24. Otherwise, the response message 92 indicates that there areno changes to be made to the scanning rules 44. In some arrangements,the client device 24 stores the scanning rules 44 in a set of XML(extensible markup language) files.

With the scanning rules 44 now in place on the client device 24, themetadata gathering circuitry 46 applies the scanning rules 44 to theoriginal versions 42 of the digital assets 22 on the client device 24 togather the metadata 48 regarding various properties of the digitalassets 22. This metadata 48 is outputted by the metadata gatheringcircuitry 46 in the form of metadata entries. Each metadata entryidentifies a particular digital asset 22 and a particular set of digitalasset properties of that particular digital asset 22 (e.g., one metadataentry per each digital asset scan). It should be understood that themetadata entries can be temporarily buffered in the client device 24(e.g., awaiting transmission to the server device 26 if the client andserver devices 24, 26 are temporarily disconnected from each other).

In some arrangements, such application of the scanning rules 44 occurson an original version 42 of a digital asset 22 just before the clientdevice circuitry 40 generates an encrypted copy 80 of that digital asset22 for storage on the subsystem 28. In another arrangement, suchapplication occurs on an original version 42 of a digital asset 22immediately after the original version 42 of the digital asset 22 hasbeen created or modified. In yet other arrangements, scanning occursroutinely at a variety of different times such as those mentioned aboveas well as periodically and in response to detected events (e.g.,copying a file, in response to a command from the server device 26, inresponse to startup of the client device 24, etc.).

When the client device 24 generates the encrypted copies 80 of thedigital assets 22 and sends the encrypted copies 80 of the digitalassets 22 to the secondary storage subsystem 28 for storage in thedigital asset repository 72, the client device 24 also sends thegathered metadata 48 to the server device 26. The metadata databasecircuitry 60 receives the metadata 48 (i.e., metadata entries) andupdates the metadata database 62 based on the metadata 48.

It should be understood that transferring the encrypted copies 80 of thedigital assets 22 to the secondary storage subsystem 28 and sending ofthe metadata 48 to the server device 26 can be performed asynchronously.That is, the client device 24 can send the metadata 48 to the serverdevice 26 at different times from when the client device 24 sends theencrypted copies 80 of the digital assets 22 to the secondary storagesubsystem 28.

In some arrangements, the client device 24 does not maintain themetadata entries once they are sent to the server device 26. However,the client device 24 does maintain certain metadata information to makecollection of metadata entries quicker.

When the server device 26 receives the metadata entries from the clientdevice 24, the server device 26 is able to process the metadata entriesto discern usage patterns (e.g., when the digital asset 22 was lastaccessed, how many times the digital assets 22 was accessed during thelast month, etc.). Since the server device 26 determines digital assetusage patterns rather than the client device 24, the performance impacton the client device 24 is minimized.

Once (i) the versions 80 of the digital assets 22 are stored in thedigital asset repository 72 of the secondary storage subsystem 28 and(ii) the metadata database 62 is updated with the gathered metadata 48,a user is now able to intelligently retrieve particular digital assets22 (illustrated by reference numeral 94 in FIG. 1). In particular, theuser is able to efficiently and effectively search for and find digitalassets 22 within the digital asset repository 72 using digital assetproperties as searching criteria. Such identification of specificdigital assets is achievable even thought the versions 80 of the digitalassets 22 are in encrypted form since the specific properties of thedigital assets 22 were gathered at the client device 24 prior toencryption.

It should be understood that one or more of the above-describedcomponents of the electronic system 20 can be implemented usingcomputerized processing circuitry and software. In particular, softwareapplications can be delivered to the client device 24, the server device26 and/or the secondary storage subsystem 28 in the form of computerprogram products 96 (illustrated generally by a diskette icon 96 in FIG.1). Such computer program products 96 include computer readable mediafor storing instructions which, when executed by the processingcircuitry 102, form the earlier-mentioned circuits. Examples of suitablecomputer readable media include tangible articles of manufacture andapparatus such as CD-ROM, flash memory, disk memory, tape memory, andthe like. Further details will now be provided with reference to thefollowing examples.

Content-Based Example

Suppose that the user wishes to retrieve only certain types of digitalassets 22, i.e., digital assets 22 containing content of a certainformat/type. In particular, suppose that the user wishes to know whichdigital assets 22 include social security numbers. To this end, the useris able to create a scanning rule 44 on the server device 26 having thefollowing format:

-   -   IF DA_INCLUDES STRING [###-##-####], ADD KEYWORD [SS#]        and then send this scanning rule 44 to the client device 24. It        should be understood that other syntax are suitable for use.

Once the client device 24 has this scanning rule 44, the client device24 is able to apply this scanning rule 44 to the digital assets 22. Inparticular, when the metadata gathering circuitry 46 applies thescanning rule 44 to an original version 42 of a digital asset 22, themetadata gathering circuitry 46 creates a metadata entry whichassociates a keyword such as “SS#” with the digital asset 22 if acharacter string having the format “###-##-####” where “#” is a numberbetween 0 and 9 exists within the original version 42 of the digitalasset 22. Otherwise, the metadata gathering circuitry 46 does not createa metadata entry.

Recall that the metadata gathering circuitry 46 is capable of applyingthe scanning rule 44 to the original versions 42 of the digital assets22 either at the time of creation or modification. Scans also run whenthere is a scanning rule change or at other times. For example, when anoriginal set of scanning rules 44 is replaced with a new set of scanningrules 44, the client device 24 may apply the new set of scanning rules44. Additionally, for digital assets 22 that change frequently (e.g.,email or PST files), the client device 24 may apply the rulesperiodically rather than after each access.

When the metadata gathering circuitry 46 sends the gathered metadata 48to the server device 26, the metadata database circuitry 60 updates themetadata database 62 based on each metadata entry of the gatheredmetadata. Accordingly, with the copied versions 80 of the digital assets22 now residing in the secondary storage subsystem 28, if the userperforms a database search on the metadata database 62 for digitalassets 22 containing a social security number (i.e., if the user queriesthe database 62 for digital assets 22 associated with the keyword“SS#”), the user will successfully identify the copied versions 80 ofthe digital assets 22 in digital asset repository 72 even though thecopied versions 80 are now in encrypted form. Thus, the user need onlyretrieve the identified digital assets 22 rather than all of the digitalassets 22 that were backed up or archived by the secondary storagesubsystem 28 at a particular time.

It should be understood that the metadata database 62 holds recordswhich are searchable using a command line interface (e.g., SQL queries).To this end, the metadata database 62 holds digital asset records whichidentify properties of digital assets 22, i.e., each digital assetrecord corresponds to a particular digital asset 22 and includesproperty data (e.g., content information, usage information, etc.)regarding that digital asset 22. In some arrangements, the metadatadatabase 62 further holds version records which identify properties ofversions of digital assets 22, i.e., each version record corresponds toa version of a particular digital asset 22 and includes property data(e.g., content information, usage information, etc.) regarding thatparticular version of the particular digital asset 22.

Such intelligent file recovery alleviates the need to decrypt and storeall of the files from the particular backup or archive routine (e.g.,the volumes may be large/massive) as in conventional retrievalapproaches. Furthermore, such intelligent retrieval alleviates the needfor the user to manually sift through all of the restored files for theparticular files as in conventional retrieval approaches. Moreover, suchoperation alleviates the need for conventional indexing at therepository 72 (e.g., un-encrypting digital assets and creating indexes,etc.).

Usage-Based Example

Suppose that the user wishes to retrieve only certain types of digitalassets 22 which were accessed during a particular time period. Forexample, suppose that the user wishes to retrieve digital assets 22having a file extension “.xyz” which were accessed during the lastmonth. To this end, the user is able to create a scanning rule 44 on theserver device 26 having the following format:

-   -   MONITOR [*.XYZ]        and then send this scanning rule 44 to the client device 24.

Once the client device 24 has received this scanning rule 44 from theserver device 26, the client device 24 is able to apply this scanningrule 44 to the digital assets 22. In particular, the client device 24 isnow configured to monitor activity regarding files with the “.xyz”extension. Along these lines, if the user accesses a digital asset 22having “filename.xyz” as the filename format, the client device 24captures metadata 48 regarding that access such as the access time(i.e., “last accessed”) for that digital asset 22. Preferably, theclient device 24 performs such monitoring and information gathering fora variety of activities such as a save operation, a move operation, etc.on the client device 24. The client device 24 then sends the collectedmetadata 48 perhaps along with other metadata 48 relating to otherdigital assets 22 to the server device 26.

The server device 26 then updates the metadata database 62 by processingthe metadata 48 describing access activity for digital assets 22 of thefilename format “filename.xyz” (e.g., the last access time) perhaps withother collected metadata 48. As a result, if the user subsequentlyperforms a database search on the metadata database 62 for digitalassets 22 of the filename format “filename.xyz” that were accessedduring the last month, the user will successfully identify the copiedversions 80 of those digital assets 22 in the digital asset repository72 even though the copied versions 80 are in encrypted form.

It should be understood that other types of usage-based searches areavailable to the user as well. For instance, in a similar manner, theuser is able to query the metadata database 62 for digital assets 22 ofthe filename format “filename.xyz” which were accessed more than acertain number of times (e.g., 3, 4, etc.) within a particular timewindow (e.g., a day, a week, a month, etc.). In this example, the serverdevice 26 participates in usage pattern determination by accessing themetadata database 62 to identify the number of times a digital asset 22has been accessed over the particular time window, i.e., the accumulatedusage-based data regarding the digital asset 22 within the metadatadatabase 62 represents a searchable usage history of the digital asset22.

It should be further understood that the electronic system's ability tomonitor digital assets 22 of specific filename formats (e.g.,“filename.xyz”) enables the electronic system 20 to ignore certainuninteresting types of activity. For example, if the client device 24performs a software upgrade to files having a filename format which isnot monitored and not of interest to the user, the activity pertainingto the upgrade is ignored by the client device 24 and thus not trackedwithin the metadata database 62 therefore saving processing resources ofthe electronic system 20.

Compound Examples

It should be understood that the metadata database 62 is capable ofstoring multiple properties regarding each digital asset 22. Inparticular, each digital asset 22 may have at least one content-basedproperty and at least one usage-based property. As a result, the user isable to create complex database searches for precise identification ofparticular digital assets 22.

An example of a complex database search based on multiple content-basedproperties is a query that includes multiple types of content. Forexample, the user may wish to identify all of the digital assets having(i) social security number and (ii) medical records as part of agovernmental compliance audit. To this end, the user creates scanningrules 44 which apply keywords to identify digital assets 22 havingsocial security numbers, medical records or both. The client device 24applies the scanning rules and gathers metadata 48, and the serverdevice 26 updates the metadata database 62 based on the metadata 48.Accordingly, the user is then able to search the metadata database 62and identify digital assets 22 having both security numbers and medicalrecords.

An example of a complex database search based on multiple usage-basedproperties is a query for digital assets 22 that were (i) accessed atleast three times in the last month and (ii) opened by a particularuser. For example, the user may have lost a laptop and is in urgent needof obtaining all files which were accessed within the last month. Again,the user creates appropriate scanning rules which are then applied bythe client device 24. Metadata is then gathered and inputted into thedatabase 62 thus enabling the user to subsequently identify digitalassets 22 fulfilling both criteria.

An example of a complex database search based on a content-basedproperty and a usage-based property is a query for digital assets 22mentioned a particular company name during a specific period of time.For example, the user may be tasked with freezing certain digital assets22 mentioning the particular company during a critical window of timefor litigation purposes.

It should be understood that nothing precludes a search from having morethan two criteria. In particular, a search of the metadata database 62can have any combination and any number of search parameters.

Further Details

It should be understood that once the specific versions 80 of thedigital assets 22 are identified based on the data search of themetadata database 62 using digital asset properties as searchingcriteria, the server device 26 coordinates retrieval of the digitalassets 22 via communications with the secondary storage subsystem 28. Inparticular, the server device 26 generates a list of digital assets 22which meet the search criteria, and then retrieves the digital assets 22based on the generated list.

For example, in response to an administrator command to place thespecific digital assets 22 in a recovery area that is external to theclient device 24, the server device 26 acquires the encrypted versions80 of the listed digital assets 22 and decrypts and stores them on theserver device 26. As another example, in response to an end-user commandto place the specific assets in an area of the client device withinwhich the original versions of digital assets originally resided, theserver device 26 directs the secondary storage subsystem 28 to send theencrypted versions 80 of the listed digital assets 22 to the clientdevice 24 and directs the client device 24 to decrypt and storedecrypted versions of the digital assets 22 in the locations of theoriginal versions 42 of the digital assets 22.

It should be understood that the user is able to restore the digitalassets 22 from the digital asset repository 72 to whatever targetstorage location the user chooses. For example, the user is able torestore the digital assets 22 to an area on a client device 24, an areaon the server device 26, or even an area which is separate from both theclient and server devices 24, 26. Further details will now be providedwith reference to FIG. 2.

FIG. 2 is a block diagram of a client device 24. Recall that theelectronic system 20 can have more than one client device 24.

As shown in FIG. 2, the client device 24 includes input/output (I/O)circuitry 100, processing circuitry 102, and memory 104. The memory 104stores a client device operating system 110, other applications and datastructures 112, the original versions 42 of the digital assets 22, thescanning rules 44, a metadata gathering application 114, and themetadata 48. As mentioned above, the metadata 48 includes historicalmetadata 116 (i.e., metadata describing access frequency, when the lastaccess occurred, who made the last access, chain of custody, etc.), andmetadata entries 118.

Recall that the metadata entries 118 are results of applying thescanning rules 44 to the original versions 42 of the digital assets 22.Accordingly, the metadata entries 118 may include information describingcontent-based properties and usage-based properties of the digitalassets 22.

It should be understood that the earlier-mentioned circuits of theclient device 24 are effectively formed by the processing circuitry 102running applications stored in the memory 104. For example, amicroprocessor of the processing circuitry 102 running the operatingsystem 110 and the metadata gathering application 114 is able to formthe metadata gathering circuitry 46. Similarly, the microprocessorrunning the operating system 110 and another application 112 (e.g., aword processing application) is able to form the client device circuitry40.

It should be further understood that a user is able to control theoperation of the client device 24 using the I/O circuitry 100 (e.g.,input commands and data through a mouse and keyboard, and outputinformation on a display). Additionally, the client device 24 is able toconnect to the communications medium 30 (also see FIG. 1) via the I/Ocircuitry 100 (e.g., a network interface, a wireless transceiver, anoptical interface, etc.). In some arrangements, the client device 24 isa well-provisioned computer (e.g., a user workstation, a laptop, aserver, etc.). In some arrangements, the client device 24 is aspecialized handheld device (e.g., a smart phone, a PDA, etc.).

If the client device 24 becomes temporarily disconnected from the serverdevice 26, the metadata gathering application 114 (also see the metadatagathering circuit 46 in FIG. 1) is constructed and arranged to bufferthe metadata entries 118 at least temporarily in the memory 104.Accordingly, the metadata gathering application 114 is capable ofsubsequently transmitting the metadata entries 118 to the server device26 once connection with the server device 26 is reestablished. Furtherdetails will now be provided with reference to FIG. 3.

FIG. 3 is a block diagram of the server device 26 which includes I/Ocircuitry 200, processing circuitry 202, and memory 204. The memory 204stores a server device operating system 210, other applications and datastructures 212, a metadata database application 214, and the metadatadatabase 62 (also see FIG. 1).

The server device 26 is capable of operating as a control center for auser (e.g., an administrator of the electronic system 20). To this end,the processing circuitry 202 executes the server device operating system210 and other applications 212 (e.g., a graphical user interface)enabling the user to carry out various operations. For example, throughthe I/O circuitry 200, the user is able to enter and convey new scanningrules 44 to each client device 24.

Additionally, the metadata database circuitry 60 (FIG. 1) is formed whenthe processing circuitry 202 runs the server device operating system 210and the metadata database engine application 214. The metadata databaseengine application 214 running on the server device 26 communicates withthe metadata gathering application 114 running on the client device 24through the communications medium 30 (FIG. 1). Accordingly, the serverdevice 26 is able to update its metadata database 62 by processing themetadata entries 118 from the client device 24.

Furthermore, the user is able to query the metadata database 62 toidentify digital assets 22 in the digital asset repository 72 forretrieval based on particular content-based and/or usage-basedproperties. As mentioned earlier, the metadata database 62 holds avariety of records which are searchable using a standard databasequeries. In particular, the metadata database 62 holds digital assetrecords 220 which correspond to particular digital assets 22 and whichidentify properties of the particular digital assets 22 (e.g., contentinformation, usage information, etc.). Additionally, the metadatadatabase 62 holds version records 222 which uniquely correspond toparticular versions 224 of digital assets 22 and which identifyproperties of the particular versions 224.

Suppose that version 1 of a digital asset 22 (e.g., a document) includesa reference to Company ABC, but that this reference was removed in asubsequent version of that digital asset 22. If the digital assetrepository 72 still includes a copy of version 1, then the metadatadatabase 62 includes a version record 222 which corresponds to version 1in the digital asset repository 72. Accordingly, the system 20 allowsthe user to identify version 1 of the digital asset 22 via a search ofthe metadata database 62 for Company ABC.

Such operation as described above speeds up the digital asset retrievalprocess, uses fewer resources than conventional approaches, and savesthe user from having to manually sift through a large number of filesthat are of no interest. Furthermore, security is maintained since thereis no need to decrypt digital assets in order to determine whether thedigital assets are relevant (e.g., whether a file relates to “CompanyABC”).

FIG. 4 is a flowchart of a procedure 300 which is performed by theelectronic system 20 when providing access to digital assets 22. In step302, the client device 24 (FIG. 1) gathers metadata 48 based on a scanof the digital assets 22 (e.g., one of a series of scans performed in anongoing manner by the client device 24). The gathered metadata 48includes metadata entries 118 (FIG. 2). Each metadata entry 118identifies a particular digital asset 22 and a particular set of digitalasset properties of that particular digital asset 22.

In step 304, the secondary storage subsystem 28 stores the digitalassets 22 in encrypted form within a digital asset repository 72 (FIG.1). Accordingly, the digital asset repository operates as a protectedsource of the digital assets 22.

In step 306, the server device 26 updates the metadata database 62 basedon the metadata entries 118. As shown in FIG. 1, the metadata database62 of the server device 26 distinct from the digital asset repository 72of the secondary storage subsystem 28 thus distinguishing theinformation in the metadata database 62 from standard operating systeminformation such as filenames, access privileges, etc.

In step 308, the server device 26 is able to identify and retrievespecific digital assets 22 within the digital asset repository 72 inresponse to a database search of the metadata database 62. Inparticular, the server device 26 is able to identify digital assets 22using digital asset properties as searching criteria (i.e.,content-based properties, usage-based properties, etc) even though theversions of the digital assets 22 stored within the digital assetrepository 72 are in encrypted form.

FIG. 5 is a flow diagram 400 which illustrates a sequence of activities400 carried out during use of the electronic system 20. In step 402, theuser creates a set of scanning rules 44 (also see FIG. 1). Examples ofcontent-based scanning rules 44 are those which enable detection ofdigital assets 22 containing certain types of content, i.e., characterstrings of a particular format, tokens, symbols, and so on.

In step 404, the user provides the scanning rules 44 to the clientdevice 24, and directs the client device 24 to gather metadata 48 (i.e.,to generate scan results) based on the scanning rules 44. In somearrangements, the client device 24 receives an entire rule set bothinitially and during updates (e.g., even if only one rule has changed oris added). In other arrangements, the user is able to add, delete andmodify the scanning rules 44 incrementally or individually at any timeduring operation of the electronic system 20. When a client device 24receives a new scanning rule 44, the client device 24 applies the newscanning rule 44 in its future operations.

In step 406, the user effectuates updating/modifying of the metadatadatabase 62 of the server device 26. For example, the user configuresthe server device 26 to receive and process the gathered metadata 48(also see the metadata entries 118 in FIG. 2) periodically duringroutine backup or archiving processes performed by the secondary storagesubsystem 28.

In step 408, the user initiates intelligent retrieval of digital assets22 from the digital asset repository 72 (FIG. 1). In particular, theuser performs a database query of the metadata database 62 using digitalasset property searching criteria. The search results take the form of alist of digital assets 22 (also see the data structures 212 in FIG. 3).

In step 410, the user retrieves only the digital assets 22 on thegenerated list. That is, only those digital assets 22 precisely meetingthe specific content type and usage pattern criteria provided by theuser in step 408 are retrieved (i.e., decrypted and stored) from therepository 72. Accordingly, less resources and time are consumedcompared to conventional retrieval approaches. Moreover, the user doesnot need to sift through a potentially massive amount of restoreddigital assets to find the digital assets of particular interest. Thedistinction between a conventional approach of decrypting all files andsearching all the files for particular files versus an improvedretrieval technique of searching first (step 408) and then decryptingonly the identified digital assets 22 (step 410) is clearly illustratedin FIG. 5.

As described above, improved techniques enable intelligent retrieval ofdigital assets 22 by storing digital assets 22 in encrypted form alongwith metadata which is gathered prior to digital asset storage. Forexample, digital assets 22 can be backed up or archived in encryptedform, and the gathered metadata can be entered into a database 62. Withthe encrypted digital assets 22 stored and the metadata available, auser is able to search the database 62 based on certain digital assetproperties (e.g., content type, usage patterns, etc.) and thus identifyrelevant digital assets 22 (or relevant versions of digital assets 22)for retrieval even though none of the digital assets 22 has yet beendecrypted. Once the individual digital assets 22 have been identified,only those digital assets 22 are retrieved (e.g., decrypted and providedto the user). Compared to conventional backup and archive systems whichretrieve all files (e.g., perhaps a massive volume), the improvedtechniques speed up the retrieval process, use fewer resources, and savethe user from having to manually sift through large numbers of filesthat are of no interest.

It should be understood that, by querying the information in themetadata database 62, the user has the ability to select digital assets22 in a manner that is unavailable on conventional archive systems whichperform full indexing. For example, the user is able to identify digitalassets 22 from the digital asset repository 72 based on frequencies withwhich the digital assets 22 were accessed (i.e., how often the digitalassets 22 were accessed). Additionally, the user is able to identifydigital assets 22 based on which users have accessed the digital assets22. Furthermore, the user is able to identify all digital assets 22derived from a particular digital asset 22 (e.g., the user is able tofind digital assets “A”, “B” and “C”, when asset “A” was copied andbecame asset “B”, and when asset “B” was then modified and emailed toanother user who stored it as asset “C”, etc.). All of these searchesand similar searches are available to the user due to ongoing gatheringof the metadata 48 from the client devices 24 (i.e., activity tracking)and availability of asset property information to the user on the serverdevice 26 (database searching of the metadata database 62).

While various embodiments of the invention have been particularly shownand described, it will be understood by those skilled in the art thatvarious changes in form and details may be made therein withoutdeparting from the spirit and scope of the invention as defined by theappended claims.

For example, FIG. 1 shows the server device 26 and the secondary storagesubsystem 28 as being separate devices which communicate through anetwork 30. In some arrangements, the secondary storage subsystem 28 isan off-the-shelf subsystem such as a traditional backup system, atraditional archive system, etc. In these arrangements, the digitalasset repository 72 is capable of being entirely separate andindependent from metadata scanning and collecting (e.g., operation ofthe digital asset repository 72 does not need to be synchronized withmetadata scanning and collecting, and no copies of the digital assets 22need to be transferred to or stored on the server device 26). Rather,the secondary storage subsystem 28 is simply customized to takedirection from both the client device 24 (e.g., when storing digitalassets 22) and the server device 26 (e.g., when retrieving digitalassets 22).

In other arrangements, the server device 26 and the secondary storagesubsystem 28 are more tightly integrated. For example, they may sharecertain components such as processors, main memory, disk memory, etc.Preferably, the metadata database 62 of the server device 26 remainsdistinct from the digital asset repository 72 of the secondary storagesubsystem 28.

An example of digital asset management environment for which at leastsome of the above-described improvements are suitable is described inInternational Application No. PCT/US2005/041773, filed on Nov. 17, 2005and entitled “SYSTEMS AND METHODS FOR MANAGING DIGITAL ASSETS”, theteachings of which are hereby incorporated by reference in theirentirety. Another example of digital asset management environment forwhich at least some of the above-described improvements are suitable isdescribed in International Application No. PCT/US2007/083195, filed onOct. 31, 2007 and entitled “SYSTEMS AND METHODS FOR INFORMATIONORGANIZATION”, the teachings of which are hereby incorporated byreference in their entirety.

Additionally, it should be understood that the server device 26 and thesecondary storage subsystem 28 were described above as being separateand independent (i.e., connected as devices on a network) by way ofexample only. In other arrangements, the server device 26 and thesecondary storage subsystem 28 are integrated and share resources (e.g.,within the same enclosure, share processors, share memory, etc.). Forinstance, in some arrangements, the digital asset repository 72 and themetadata database 62 are implemented as one database in combination withseparate tables in a tightly integrated manner.

Furthermore, the client devices 24 were described above as being primarystorage devices (e.g., user workstations, laptops, smart devices, etc.)by way of example only. It should be understood that the client devices24 may take a variety of other forms such as network attached storage,remote or secondary storage, and so on.

Additionally, the client devices 24 were described above as performingscans around the time of digital asset access. The client devices 24 mayalso carry out scanning just prior to digital asset encryption andtransferring the encrypted versions 80 of the digital assets 22 to thesecondary storage subsystem 28.

Furthermore, it should be understood that the digital asset retrievalprocess was described above as including decryption of the digitalassets 22 by way of example only. In some situations (e.g.,administrative restores, for litigation purposes, etc.), decryption maynot be desired or may be preferably delayed. In such situations,retrieval of digital assets 22 from the repository 72 (FIG. 1) involvesfetching copy versions 80 of the digital assets 22 from the repository72 and maintaining these copy versions 80 in encrypted form at adesignated location. In these situations, an authorized user may holdthe key(s) or have access to the key(s) to control decryption of thedigital assets 22 at a later time.

Additionally, it should be understood that the communications media 30was illustrated as a network cloud (e.g., a computerized network) inFIG. 1 by way of example only. It should be understood that a variety oftopologies are suitable for use for the electronic system 20, e.g.,point-to-point, backbone or multi-drop bus, loop, irregular, and so on.

1. In an electronic system, a method of providing access to digitalassets, the method comprising: gathering metadata based on a scan of thedigital assets, the gathered metadata including metadata entries, eachmetadata entry identifying a particular digital asset and a particularset of digital asset properties of that particular digital asset; aftergathering the metadata, storing the digital assets in encrypted formwithin a digital asset repository of the electronic system, the digitalasset repository operating as a protected source of the digital assets;and updating a metadata database of the electronic system based on themetadata entries, the metadata database being distinct from the digitalasset repository; wherein, while the digital assets are stored in thedigital asset repository in encrypted form, specific digital assetswithin the digital asset repository are identifiable in response to adatabase search of the metadata database, the database search usingdigital asset properties as searching criteria; wherein the electronicsystem includes a client device and a server device; wherein gatheringthe metadata based on the scan of the digital assets includes (i)scanning original versions of the digital assets on the client device,the original version of the digital assets being in non-encrypted form,and (ii) generating, as the metadata entries, a set of scan results onthe client device based on scanning the original versions of the digitalassets; wherein updating the metadata database of the electronic systembased on the metadata entries includes (i) communicating the set of scanresults from the client device to the server device through a network,and (ii) modifying the metadata database based on the set of scanresults from the client device, the metadata database residing on theserver device; wherein scanning the original versions of the digitalassets on the client device includes: obtaining a set of scanning rulesfrom the server device, and applying the set of scanning rules to theoriginal versions of the digital assets to identify, within the set ofscan results, digital asset properties of the digital assets; andwherein the client device is constructed and arranged to periodicallysend a scanning rule update request to the server device; and whereinobtaining the set of scanning rules from the server device includes:receiving a new set of scanning rules from the server device in responseto a particular scanning rule update request, and replacing a previousset of scanning rules on the client device with the new set of scanningrules, the new set of scanning rules including at least one scanningrule with did not exist in the previous set of scanning rules.
 2. Amethod as in claim 1 wherein the set of scanning rules includes ausage-based scanning rule; and wherein applying the set of scanningrules to the original versions of the digital assets includes:monitoring access of a digital asset based on the usage-based scanningrule to obtain usage-based data regarding the digital asset, theusage-based data representing at least a portion of usage history of thedigital asset.
 3. A method as in claim 1 wherein the set of scanningrules includes a content-based scanning rule; and wherein applying theset of scanning rules to the original versions of the digital assetsincludes: identifying whether a specific type of content resides withineach digital asset based on a comparison of content of that digitalasset and the content-based scanning rule.
 4. A method as in claim 1wherein applying the set of scanning rules to the original versions ofthe digital assets to identify digital asset properties of the digitalassets includes: running a metadata gathering application on the clientdevice to generate the set of scan results, the metadata gatheringapplication being constructed and arranged to communicate with ametadata database engine application running on the server devicethrough the network.
 5. A method as in claim 4, further comprising:buffering the set of scan results in a temporary cache on the clientdevice while the metadata gathering application is out of communicationwith the metadata database engine application in response to the clientdevice becoming disconnected from the server device, and conveying theset of scan results from the temporary cache on the client device to themetadata database engine application in response to the client devicereconnecting with the server device through the network.
 6. A method asin claim 4 wherein storing the digital assets in encrypted form withinthe digital asset repository of the electronic system includes: afterapplying the set of scanning rules to the original versions of thedigital assets, encrypting the original versions of the digital assetson the client device to form copies of the digital assets in encryptedform, and transferring the copies of the digital assets in encryptedform from the client device to a digital asset repository applicationthrough the network, the digital asset repository application beingconstructed and arrange to store the copies of the digital assets inencrypted form within the digital asset repository.
 7. A method as inclaim 6 wherein transferring the copies of the digital assets inencrypted form includes: conveying the copies of the digital assets inencrypted form from the client device to a storage subsystem which (i)holds the digital asset repository and (ii) runs the digital assetrepository application, the storage subsystem being external to both theclient device and the server device.
 8. A method as in claim 4, furthercomprising: on the metadata database, performing the database searchusing digital asset properties as searching criteria to generate a listof specific digital assets within the digital asset repository; andretrieving the specific digital assets from the digital asset repositorybased on the generated list.
 9. A method as in claim 8 wherein themetadata database includes digital asset records, each digital assetrecord identifying a particular digital asset residing in the digitalasset repository and describing specific digital asset properties ofthat particular digital asset; and wherein performing the databasesearch using digital asset properties as searching criteria includes:searching the metadata database for digital asset records indicatingthat a specific type of content resides in a particular digital asset,and putting an identifier of that particular digital asset on the listwhen the digital asset record indicating that the particular digitalasset indicates that the specific type of content resides in theparticular digital asset.
 10. A method as in claim 8 wherein thedatabase search is performed in response to an administrator command toplace the specific digital assets in a recovery area that is external tothe client device; and wherein retrieving the specific digital assetsfrom the digital asset repository based on the generated list includes:decrypting the specific digital assets from the digital asset repositoryto generate restored versions of the specific digital assets, andstoring the restored versions of the specific digital assets in therecovery area that is external to the client device.
 11. A method as inclaim 8 wherein the database search is performed in response to anend-user command to place the specific digital assets in an area of theclient device within which the original versions of digital assetsoriginally resided; and wherein retrieving the specific digital assetsfrom the digital asset repository based on the generated list includes:decrypting the specific digital assets from the digital asset repositoryto generate restored versions of the specific digital assets, andstoring the restored versions of the specific digital assets in the areaof the client device within which the original versions of digitalassets originally resided.
 12. A method as in claim 8 wherein themetadata database includes version records, each version recordidentifying a particular version of a digital asset residing in thedigital asset repository and describing specific digital assetproperties of that particular version of that particular digital asset;and wherein performing the database search using digital assetproperties as searching criteria includes: querying the metadatadatabase for relevant version records to identify relevant versions ofdigital assets within the digital asset repository.
 13. A method as inclaim 8 wherein the metadata database includes digital asset records,each digital asset record identifying a particular digital assetresiding in the digital asset repository and describing specific digitalasset properties of that particular digital asset; and whereinperforming the database search using digital asset properties assearching criteria includes: searching the metadata database for digitalasset records describing a specific digital asset usage pattern, andputting an identifier of a particular digital asset on the list when thedigital asset record identifying the particular digital asset describesthe specific digital asset usage pattern.
 14. A method as in claim 1wherein the digital asset repository includes a backup subsystem; andwherein storing the digital assets in encrypted form within the digitalasset repository includes performing a backup operation to back up thedigital assets on the backup subsystem in encrypted form while theoriginal versions of the digital assets continue to reside on the clientdevice in non-encrypted form, the original versions of the digitalassets being maintained on the client device in non-encrypted form aftercompletion of the backup operation.
 15. A method as in claim 14, furthercomprising: after completion of the backup operation and in response toa loss of an original version of a particular digital asset on theclient device, performing a retrieval operation to retrieve theparticular digital asset from the backup subsystem and placing arestored version of the particular digital asset on the client device,the restored version of the particular digital asset being maintained onthe client device in non-encrypted form after completion of theretrieval operation and while the particular digital asset remainsbacked up on the backup subsystem in encrypted form.
 16. An electronicsystem to provide access to digital assets, the electronic systemcomprising: metadata gathering circuitry constructed and arranged togather metadata based on a scan of the digital assets, the gatheredmetadata including metadata entries, each metadata entry identifying aparticular digital asset and a particular set of digital assetproperties of that particular digital asset; digital asset storagecircuitry constructed and arranged to, after the metadata is gathered,store the digital assets in encrypted form within a digital assetrepository, the digital asset repository operating as a protected sourceof the digital assets; and metadata database circuitry coupled to themetadata gathering circuitry and the digital asset storage circuitry,the metadata database circuitry being constructed and arranged to updatea metadata database based on the metadata entries, the metadata databasebeing distinct from the digital asset repository; wherein, while thedigital assets are stored in the digital asset repository in encryptedform, specific digital assets within the digital asset repository areidentifiable in response to a database search of the metadata database,the database search using digital asset properties as searchingcriteria; wherein the electronic system includes a client device whichhas the metadata gathering circuitry, and a server device which has themetadata database circuitry; wherein the metadata gathering circuitry,when gathering the metadata based on the scan of the digital assets, isconstructed and arranged to (i) scan original versions of the digitalassets on the client device, the original version of the digital assetsbeing in non-encrypted form, and (ii) generate, as the metadata entries,a set of scan results on the client device based on scanning theoriginal versions of the digital assets; wherein the metadata databasecircuitry, when updating the metadata database of the electronic systembased on the metadata entries, is constructed and arranged to (i)communicate the set of scan results from the client device to the serverdevice through a network, and (ii) modify the metadata database based onthe set of scan results from the client device, the metadata databaseresiding on the server device; wherein the metadata gathering circuitry,when scanning the original versions of the digital assets on the clientdevice, is constructed and arranged to: obtain a set of scanning rulesfrom the server device, and apply the set of scanning rules to theoriginal versions of the digital assets to identify, within the set ofscan results, digital asset properties of the digital assets; whereinthe client device is constructed and arranged to periodically send ascanning rule update request to the server device; and wherein themetadata gathering circuitry, when obtaining the set of scanning rulesfrom the server device, is constructed and arranged to: receive a newset of scanning rules from the server device in response to a particularscanning rule update request, and replace a previous set of scanningrules on the client device with the new set of scanning rules, the newset of scanning rules including at least one scanning rule with did notexist in the previous set of scanning rules.
 17. An electronic system asin claim 16 wherein the metadata gathering circuitry includes processingcircuitry and memory coupled to the processing circuitry, the memorystoring a metadata gathering application; and wherein the metadatagathering circuitry, when applying the set of scanning rules to theoriginal versions of the digital assets to identify digital assetproperties of the digital assets, is constructed and arranged to: usingthe processing circuitry, run the metadata gathering application storedin the memory to generate the set of scan results, the metadatagathering application being constructed and arranged to communicate witha metadata database engine application running on the server devicethrough the network.
 18. An electronic system as in claim 17, furthercomprising: a temporary cache to buffer the set of scan results whilethe metadata gathering application is out of communication with themetadata database engine application in response to the client devicebecoming disconnected from the server device, and input/output circuitryto convey the set of scan results from the temporary cache to themetadata database engine application in response to the client devicereconnecting with the server device through the network.
 19. A computerprogram product including a computer readable medium having instructionsstored thereon which, when executed by computerized equipment, directthe computerized equipment to: gather metadata based on a scan of thedigital assets, the gathered metadata including metadata entries, eachmetadata entry identifying a particular digital asset and a particularset of digital asset properties of that particular digital asset; aftergathering the metadata, store the digital assets in encrypted formwithin a digital asset repository of an electronic system, the digitalasset repository operating as a protected source of the digital assets;and update a metadata database of the electronic system based on themetadata entries, the metadata database being distinct from the digitalasset repository; wherein, while the digital assets are stored in thedigital asset repository in encrypted form, specific digital assetswithin the digital asset repository are identifiable in response to adatabase search of the metadata database, the database search usingdigital asset properties as searching criteria; wherein the electronicsystem includes a client device and a server device; wherein gatheringthe metadata based on the scan of the digital assets includes (i)scanning original versions of the digital assets on the client device,the original version of the digital assets being in non-encrypted form,and (ii) generating, as the metadata entries, a set of scan results onthe client device based on scanning the original versions of the digitalassets; wherein updating the metadata database of the electronic systembased on the metadata entries includes (i) communicating the set of scanresults from the client device to the server device through a network,and (ii) modifying the metadata database based on the set of scanresults from the client device, the metadata database residing on theserver device; wherein scanning the original versions of the digitalassets on the client device includes: obtaining a set of scanning rulesfrom the server device, and applying the set of scanning rules to theoriginal versions of the digital assets to identify, within the set ofscan results, digital asset properties of the digital assets; andwherein the client device is constructed and arranged to periodicallysend a scanning rule update request to the server device; and whereinobtaining the set of scanning rules from the server device includes:receiving a new set of scanning rules from the server device in responseto a particular scanning rule update request, and replacing a previousset of scanning rules on the client device with the new set of scanningrules, the new set of scanning rules including at least one scanningrule with did not exist in the previous set of scanning rules.
 20. Acomputer program product as in claim 19 wherein applying the set ofscanning rules to the original versions of the digital assets toidentify digital asset properties of the digital assets includes:running a metadata gathering application on the client device togenerate the set of scan results, the metadata gathering applicationbeing constructed and arranged to communicate with a metadata databaseengine application running on the server device through the network. 21.A computer program product as in claim 20 wherein the instructions, whenexecuted by the computerized equipment, further direct the computerizedequipment to: buffer the set of scan results in a temporary cache on theclient device while the metadata gathering application is out ofcommunication with the metadata database engine application in responseto the client device becoming disconnected from the server device, andconvey the set of scan results from the temporary cache on the clientdevice to the metadata database engine application in response to theclient device reconnecting with the server device through the network.